Zangune
Mar 17 2016

When will the free shell be back to full capacity?
4  2K+ {{tagitem.name}}
Greetings, as far as I know days ago the old free shell server was substituted by new one.
Since then, I had some problems with xShellz.
I use PuTTY 0.67, the latest one, but problems appeared in version 0.66, too.
If I try to use long commands from history, then the line will not show the whole text, in example:

<ngune/ | grep total | grep --only-matching "^\w*\b"

Please note I did not hide a part of the above line, this is exactly how I can see it in PuTTY.
Another problem is about the nano text editor:

Zangune@xshellzfreenew:~$ nano /home/Zangune/.bash_history
Error opening terminal: putty.

Actually I don't know if this particular problem can be fixed client side, too, but I know that nano used to work with my shell client before the server change and that PuTTY is a very common shell client, so the problem may affect a lot of people.
Unless I am wrong in some way, can you please tell me:
Are you aware of these and similar problems?
If so, do you plan to fix them?
If so, when (at least approximately) will they be fixed?
Regards.
Zangune I have no issues using nano or putty and I have had no one else come to us with any complaints.
saapete    Mar 22 2016
Thanks for your reply, saapete.
As far as I know, the problem should be caused by a missing package: ncurses-term.
From the Debian packages page of ncurses-term (https://packages.debian.org/en/jessie/ncurses-term): "The ncurses library routines are a terminal-independent method of updating character screens with reasonable optimization. This package contains all of the numerous terminal definitions not found in the ncurses-base package.".
The "putty" terminal definition should be there.
I believe this package was installed in the old server and I know (dpkg -s ncurses-term) it is not installed in the new one.
Some time ago (I cannot remember exactly the date, but at least months before the server attack), I modified a string in PuTTY: in the PuTTY Configuration window, in Connection > Data, in "terminal-type string" I set "putty".
I forget about that (I am sorry) and the reason I changed that string was to try to fix some visualization problems.
Now I changed the string to "xterm" and it seems the problem in this thread is gone.
The installation of ncurses-term would be appreciated, if possible.
Regards.
Zangune    Mar 22 2016
ncurses-term is installed on the free server and added to the xMaster list.
Staff StephenS    Apr 13 2016
Thank you very much StephenS.
Zangune    May 06 2016

Please Login or Sign Up to leave a reply.